\section{Deadline Class Reference}
\label{a00049}\index{BPMVE\_\-XPDL\_\-Library::Deadline@{BPMVE\_\-XPDL\_\-Library::Deadline}}


Deadlines are used To raise an Exception upon the expiration of a specific period of time. Note that BPMN provides the Timer \doxyref{Event}{p.}{a00058} as a general method for handling Deadlines. See sction 7.6.4.5.11. Upon the arrival of a deadline, an Exception \doxyref{Condition}{p.}{a00034} is raised AND the appropriate Exception transitions are followed. If the deadline is synchronous, then the activity is terminated Before flow continues on the Exception path. If the deadline is asynchronous, then an implicit AND SPLIT is performed, AND a new thread of processing is started on the appropriate Exception transition. Asynchronous exceptions can cause side effects, AND should be used carefully. Some of these side effects are discussed later in this section.  


\subsection*{Properties}
\begin{DoxyCompactItemize}
\item 
ExecutionSyncMode {\bf Execution}\hspace{0.3cm}{\ttfamily  [get, set]}
\item 
{\bf ExpressionType} {\bf DeadlineDuration}\hspace{0.3cm}{\ttfamily  [get, set]}
\item 
string {\bf ExceptionName}\hspace{0.3cm}{\ttfamily  [get, set]}
\end{DoxyCompactItemize}


\subsection{Detailed Description}


Definition at line 18 of file Deadline.cs.



\subsection{Property Documentation}
\index{BPMVE\_\-XPDL\_\-Library::Deadline@{BPMVE\_\-XPDL\_\-Library::Deadline}!Execution@{Execution}}
\index{Execution@{Execution}!BPMVE_XPDL_Library::Deadline@{BPMVE\_\-XPDL\_\-Library::Deadline}}
\subsubsection[{Execution}]{\setlength{\rightskip}{0pt plus 5cm}ExecutionSyncMode Execution\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00049_a645267e60bbe2ec9fe076eccac14383c}


Define the System behaviour on raising the arrival of the deadline ASYNCHR -\/ The deadline is To be raised asynchronously. This is an implicit AND SPLIT operation, where the activity continues AND another thread is started following the named Exception transition. Another deadline may occur on the same activity, because it continues running. SYNCHR -\/ The activity is Completed abnormally AND flow continues on the named Exception transition. 



Definition at line 29 of file Deadline.cs.

\index{BPMVE\_\-XPDL\_\-Library::Deadline@{BPMVE\_\-XPDL\_\-Library::Deadline}!DeadlineDuration@{DeadlineDuration}}
\index{DeadlineDuration@{DeadlineDuration}!BPMVE_XPDL_Library::Deadline@{BPMVE\_\-XPDL\_\-Library::Deadline}}
\subsubsection[{DeadlineDuration}]{\setlength{\rightskip}{0pt plus 5cm}{\bf ExpressionType} DeadlineDuration\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00049_a1c39d16e4897943acf583de6a3c8fa1e}


An expression indicating the time of the deadline. This expression is implementation dependent AND may include at least: Times relative To the beginning of the activity. (2 days) Fixed times (January 1) OR (January 1, 2002) Times computed using relevant Data field (varName days). 



Definition at line 39 of file Deadline.cs.

\index{BPMVE\_\-XPDL\_\-Library::Deadline@{BPMVE\_\-XPDL\_\-Library::Deadline}!ExceptionName@{ExceptionName}}
\index{ExceptionName@{ExceptionName}!BPMVE_XPDL_Library::Deadline@{BPMVE\_\-XPDL\_\-Library::Deadline}}
\subsubsection[{ExceptionName}]{\setlength{\rightskip}{0pt plus 5cm}string ExceptionName\hspace{0.3cm}{\ttfamily  [get, set]}}\label{a00049_abb3cc84919c5855653f5002f911be354}


The name of the Exception To be raised on arrival of the deadline. This name should match that specified in Transition/Condition/Expression. 



Definition at line 47 of file Deadline.cs.

